Notification for a prioritized media path for a communication session

ABSTRACT

Techniques for notification for a prioritized media path for a communication session are described. According to various embodiments, a communication session is authenticated with a communication service. The communication service interacts with an Internet Protocol (IP) network and a wireless access network to cause the communication session to be routed across a prioritized media path.

BACKGROUND

Modern communication systems have an array of capabilities, includingintegration of various communication modalities with different services.For example, systems that enable users to share and collaborate increating and modifying various types of documents and content may beintegrated with multimodal communication systems providing differentkinds of communication and collaboration capabilities. Such integratedsystems are sometimes referred to as Unified Communication (UC) systems.

While UC systems provide for increased flexibility in communications,they also present a number of implementation challenges. For instance,UC data flows are typically routed over networks that are unaware ofattributes of the individual flows. Thus, challenges arise in selectingan optimum routing path for a UC data flow, and in responding to changesin signal quality across a data path for a UC data flow.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Techniques for notification for a prioritized media path for acommunication session are described. According to various embodiments, acommunication session is authenticated with a communication service. Thecommunication service interacts with an Internet Protocol (IP) networkand a wireless access network to cause the communication session to berouted across a prioritized media path.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different instances in thedescription and the figures may indicate similar or identical items.

FIG. 1 is an illustration of an environment in an example implementationthat is operable to employ techniques discussed herein.

FIG. 2 illustrates an example implementation scenario for propagatinginstructions for handling a communication session in accordance with oneor more embodiments.

FIG. 3 illustrates an example implementation scenario for prioritizing acommunication session in accordance with one or more embodiments.

FIG. 4 is a flow diagram that describes steps in a method for causing acommunication session to be routed to a prioritized media path inaccordance with one or more embodiments.

FIG. 5 is a flow diagram that describes steps in a method for causing acommunication session to be rerouted in accordance with one or moreembodiments.

FIG. 6 illustrates an example system and computing device as describedwith reference to FIG. 1, which are configured to implement embodimentsof techniques described herein.

DETAILED DESCRIPTION

Overview

Techniques for notification for a prioritized media path for acommunication session are described. A communication session, forinstance, represents an exchange of communication media betweendifferent nodes in a network. Examples of a communication sessioninclude a Voice over Internet Protocol (VoIP) call, a video call, textmessaging, a file transfer, and/or combinations thereof. In at leastsome embodiments, a communication session represents a UnifiedCommunication (UC) session.

According to various implementations, a communication session between aclient device and an endpoint device is initiated via a communicationservice, such as a web-based UC service. A media flow of thecommunication session is routed from the client device across anInternet Protocol (IP) network to a radio access network, where it iswirelessly transmitted to the endpoint device. In at least someimplementations, the IP network represents an IP packet core networksuch as an Evolved Packet Core (EPC) network, and the radio accessnetwork represents a high-speed wireless network, such as a UniversalTerrestrial Radio Access Network (UTRAN) network. The IP network and theUTRAN network, for instance, represent components of a mobile broadbandnetwork, such as a Long-Term Evolution (LTE) network.

Continuing with the example scenario, the communication serviceascertains that the communication session represents an authenticatedmedia flow that is entitled to receive a prioritized service level. Auser involved in the communication session, for instance, has a useraccount with the communication service that entitles the user to aprioritized service level for the communication session. Accordingly,the communication service interacts with the IP network and the radionetwork to cause the communication session to be moved to a prioritizedmedia path. In at least some implementations, the communication serviceinteracts with the IP network and the radio network via a network proxythat acts as an intermediary for the communication service.

Based on this interaction, the IP network marks a media flow of thecommunication session with a prioritized service marking. For instance,data packets of the communication session are marked with a prioritizedquality of service (QoS) marking. Accordingly, the IP network moves thecommunication session to a prioritized routing path across the IPnetwork. Further based on the interaction by the communication service,the radio network moves the communication session to a prioritizedwireless channel. The radio network, for instance, moves thecommunication session from a standard bearer channel to a dedicatedbearer channel that provides the communication session with a higherairtime prioritization than does the standard bearer channel.

Thus, techniques described herein provide communication sessions thatare authenticated with a communication service with prioritized serviceover other, non-authenticated media flows. This not only providesprioritized service to authenticated users, but protects networkresources from interference and malicious activities that may resultfrom allowing non-authenticated media flows to access the networkresources.

In the following discussion, an example environment is first describedthat is operable to employ techniques described herein. Next, a sectionentitled “Propagating Attributes of Communication Sessions” discussessome example ways for notifying different communication components ofattributes of communication sessions. Following this, a section entitled“Example Implementation Scenarios” describes some example implementationscenarios in accordance with one or more embodiments. Next, a sectionentitled “Example Procedures” describes some example procedures inaccordance with one or more embodiments. Finally, a section entitled“Example System and Device” describes an example system and device thatare operable to employ techniques discussed herein in accordance withone or more embodiments.

Having presented an overview of example implementations in accordancewith one or more embodiments, consider now an example environment inwhich example implementations may by employed.

Example Environment

FIG. 1 is an illustration of an environment 100 in an exampleimplementation that is operable to employ techniques for notificationfor a prioritized media path for a communication session describedherein. Generally, the environment 100 includes various devices,services, and networks that enable communication via a variety ofdifferent modalities. For instance, the environment 100 includes aclient device 102 connected to one or more networks 104. The clientdevice 102 may be configured in a variety of ways, such as a traditionalcomputer (e.g., a desktop personal computer, laptop computer, and soon), a mobile station, an entertainment appliance, a smartphone, anetbook, a game console, a handheld device (e.g., a tablet), a wearabledevice, and so forth.

The network 104 is representative of any suitable network and/orcombination of networks that provides the client device 102 withconnectivity to various devices and services. The network 104 mayprovide the client device 102 with connectivity via a variety ofdifferent wired and/or wireless connectivity technologies, such asbroadband cable, digital subscriber line (DSL), wireless dataconnectivity (e.g., WiFi™), wireless cellular, T-carrier (e.g., T1),Ethernet, and so forth.

The environment 100 further includes a communication service 106, whichis representative of a service to perform various tasks for managementof communication between the client device 102 and an endpoint device108. Generally, the endpoint device 108 is representative of any devicewith which the client device 102 may exchange data, such as an end-userdevice connected to the network 104. The communication service 106, forinstance, can manage initiation, moderation, and termination ofcommunication sessions. Examples of the communication service 106include a VoIP service, an online conferencing service, a UC service,and so forth. In at least some embodiments, the communication service106 may be implemented as or be connected to a private branch exchange(PBX) in communication with a Public Switched Telephone Network (“PSTN”)to enable voice communication between the client device 102 and theendpoint device 108.

In at least some embodiments, the client device 102 is configured tointerface with the communication service 106 via a communication client110 a to enable communication between the client device 102 and theendpoint device 108. The communication client 110 a is representative offunctionality (e.g., an application and/or service) to enable differentforms of communication via the client device 102. Examples of thecommunication client 110 a include a voice communication client (e.g., aVoIP client), a video communication client, a messaging application, acontent sharing application, and combinations thereof. The communicationclient 110 a, for instance, enables different communication modalitiesto be combined to provide diverse communication scenarios.

According to one or more implementations, the communication client 110 arepresents an application that is installed on the client device 102.Additionally or alternatively, the communication client 110 a can beimplemented as a remote application, such as accessed via a web browser,a web application, and so forth.

The endpoint device 108 includes a communication client 110 b, whichrepresents an instance of the communication client 110 a that can beleveraged by the endpoint device 108 to communicate with other devices.For instance, a communication session between the client device 102 andthe endpoint device 108 represents an exchange of communication mediabetween the communication client 110 a and the communication client 110b.

The network 104 further includes various component networks that enablerouting of data (e.g., communication session data) between the clientdevice 102 and the endpoint device 108. For instance, the network 104includes one or more core networks 112 and one or more radio networks114. The core network 112 is representative of functionality forconverting packet-based data into a form that can be transmitted by theradio network 114 to various devices, such as the endpoint device 108.In at least some implementations, the core network 112 represents anEvolved Packet Core (EPC) network. The radio network 114 isrepresentative of one or more radio access networks for wirelesstransmission of data to various devices and entities, such as to theendpoint device 108 and the client device 102. In at least someimplementations, the radio network 114 represents an evolved UTRAN(e-UTRAN). The core network 112 and the radio network 114, for instance,are implemented by an enterprise wireless carrier, such as a wirelesscellular network carrier.

The core network 112 includes various functionalities for processing ofcommunication session data, such as a traffic processor 116 and a policymodule 118. The traffic processor 116 is representative of functionalityfor ascertaining attributes of media flows of communication sessions andfor applying communication policies 120 to the media flows. Generally,the communication policies 120 specify various parameters and actions tobe applied to media flows. For instance, the communication policies 120specify quality of service (QoS) markings to be applied to media flows.The communication policies 120, for example, specify QoS in terms ofDifferentiated Services Code Point (DSCP) markings that are to beapplied to particular media flows.

In at least some implementations, the communication policies 120 aresession-specific, e.g., are defined with respect to discrete mediaflows. For instance, a particular communication policy 120 can beapplied by the traffic processor 116 based on an identifier for a mediaflow, such as based on devices and/or users involved in the media flow.

The policy module 118 is representative of functionality for interfacingwith the traffic processor 116 and for configuring the communicationpolicies 120. As further detailed below, the communication service 106can communication attributes of a communication session to a proxymodule 122, which translates the attributes into a form that isunderstood by the policy module 118. The proxy module 122 communicatesthe translated attributes to the policy module 118, which uses thetranslated attributes to configure a communication policy 120 for thecommunication session. The traffic processor 116 applies thecommunication policy 120 to a media flow of the communication session.

Generally, the proxy module 122 is representative of functionality toreceive attributes of a communication session from the communicationservice 106, and to translate the attributes into different forms. Forinstance, the communication service 106 includes a session module 124that is configured at ascertain attributes of a communication session,and to propagate attributes of the communication session to variousentities. For instance, the session module 124 communicates attributesof a communication session to the proxy module 122 according to aprotocol utilized by the communication service 106. The proxy module 122translates the attributes into a different protocol utilized by the corenetwork 112. The proxy module 122 then communicates the translatedattributes to the policy module 118 for use in configuring acommunication policy 120.

Further to the environment 100, the radio network 114 includes variousinfrastructure components for enabling transmission of wireless signal,including network nodes 126. Generally, the network nodes 126 representhardware and logic for transmitting wireless signal to various devices,such as the endpoint device 108 and the client device 102. In at leastsome implementations, the network nodes 126 represent Evolved Node B(eNodeB) elements of the radio network 114.

While the environment 100 is discussed with reference to particularexamples of devices and functionalities, it is to be appreciated thattechniques for notification for a prioritized media path for acommunication session described herein can be employed with a variety ofdifferent devices and in a variety of different network architectures inaccordance with the claimed embodiments.

Having described an example environment in which the techniquesdescribed herein may operate, consider now a discussion of example waysof propagating various attributes of communication sessions incommunication systems in accordance with one or more embodiments.

Propagating Attributes of Communication Sessions

According to various embodiments, techniques can be employed todynamically enlighten various network components with information aboutcommunication sessions. For instance, notification events can begenerated that include various attributes of communication sessions. Thenotification events can be propagated to different entities further totechniques for notification for a prioritized media path for acommunication session discussed herein.

In at least some embodiments, notification events can be configuredusing a communication application programming interface (API) that canbe leveraged to configure and communicate session information to variousnetwork components involved in a communication session. For example, thecommunication API can identify dialogue events and session events forwhich attributes of a communication session can be identified. Consider,for instance, the following events and attributes that may be conveyedvia a notification event generated by the communication API:

Dialogue Events—

These events apply to various portions of a communication session, suchas the start, update, and end of a communication session. A dialogueevent can include one or more of the following example attributes.

(1) Timestamp: This attribute can be leveraged to specify timestamps fora start of a communication session, updates that occur during acommunication session, and an end (e.g., termination) of a communicationsession.

(2) Source IP Address: This attribute can be leveraged to specify an IPaddress for a device that is a source of media during a communicationsession, e.g., a device that initiates a communication session.

(3) Destination IP Address: This attribute can be leveraged to specifyan IP address for a device that is to receive media as part of acommunication session.

(4) Transport Type: This attribute can be leveraged to specify atransport type or combination of transport types for a communicationsession. Examples of transport types include Transmission ControlProtocol (TCP), User Datagram Protocol (UDP), and so forth.

(5) Source Port: this attribute can be leveraged to specify anidentifier for a port at a source device, e.g., a source deviceidentified by the Source IP Address referenced above.

(6) Destination Port: This attribute can be leveraged to specify anidentifier for a port at a destination device, e.g., a destinationdevice identified by the Destination IP Address referenced above.

(7) Media Type: This attribute can be leveraged to specify a media typeand/or types that are to be transmitted and/or are being transmitted aspart of a communication session. As discussed elsewhere herein, thecommunication session can involve multiple different types of media.Thus, the Media Type attribute can be employed to identify media typesin a communication session, such as for applying the communicationpolicies discussed herein.

(8) Bandwidth Estimation: This attribute can be leveraged to specify anestimated bandwidth that is to be allocated for a communication session.The estimated bandwidth, for instance, can be based on various factors,such as a privilege level associated with a user, type and/or types ofmedia included in a communication session, and so forth.

(9) To: This attribute can be leveraged to identify a user to whichmedia in a communication session is to be transmitted.

(10) From: This attribute can be leveraged to identify a user from whichmedia and a communication session is transmitted.

(11) Error Code: This attribute can be leveraged to specify variouserror codes for pairs that may occur as part of a communication session.For example, errors can include errors that occur during initiation thecommunication session, errors that occurred during a communicationsession, errors that occur when a communication session is terminated,and so forth.

(12) Class of Service: This attribute can be leveraged to specify aclass of service (CoS) to be applied to a communication session. Classof service may be specified in various ways, such as QoS markings, DSCPmarkings, and so forth. Examples of class of service include best-efforttraffic (BE), Expedited Forwarding (EF) Assured Forwarding (AF), and soon.

Session Problem Events—

These events can be generated and applied when a communication sessionexperiences errors, performance degradation, and so forth. A sessionproblem event may include one or more of the attributes discussed abovewith reference to Dialogue Events, and may also include one or more ofthe following attributes.

(1) Mean Opinion Score (MOS) Degradation: This attribute can beleveraged to specify a MOS for a communication session. The attribute,for instance, can be used to indicate that an overall quality of acommunication session has decreased.

(2) Jitter Inter-Arrival Time: This attribute can be leveraged tospecify jitter values for a communication session. The attribute, forinstance, can be used to indicate that a jitter value or values haveincreased, e.g., have exceeded a specified jitter value threshold.

(3) Packet Loss Rate: This attribute can be leveraged to specify apacket loss rate for a communication session. The attribute, forinstance, can be used to indicate that a packet loss rate has increased,e.g., has exceeded a specified packet loss rate value threshold.

(4) Round Trip Delay (RTD): This attribute can be leveraged to specifyRTD values for packets in communication sessions. The attribute, forinstance, can be used to indicate that RTD values for packets haveincreased, e.g., have exceeded a specified RTD value threshold.

(5) Concealment Ratio: This attribute can be leveraged to specify acumulative ratio of concealment time over speech time observed afterstarting a communication session. The attribute, for instance, can beused to specify that a concealment ratio has increased, e.g., hasexceeded a specified concealment ratio value threshold.

Thus, various notifications discussed herein can include one or more ofthe attributes discussed above and can be used to propagate theattributes to various entities.

Having described an example ways of propagating attributes ofcommunication sessions, consider now some example implementationscenarios for notification for a prioritized media path for acommunication session in accordance with one or more embodiments.

Example Implementation Scenarios

The following section describes example implementation scenarios fornotification for a prioritized media path for a communication session inaccordance with one or more embodiments. The implementation scenariosmay be implemented in the environment 100 discussed above, and/or anyother suitable environment.

FIG. 2 illustrates an example implementation scenario 200 forpropagating instructions for handling a communication session inaccordance with one or more implementations. The scenario 200 includesvarious entities and components introduced above with reference to theenvironment 100.

In the scenario 200, the communication client 110 a of the client device102 initiates a communication session 202 with the communication client110 b of the endpoint device 108. For instance, a user of the clientdevice 102 interacts with the communication client 110 a to initiate thecommunication session 202, such as by dialing a telephone number,selecting a contact, selecting a hyperlink, and so forth. Accordingly,the communication session 202 is established, which represents a flow ofcommunication media from the client device 102 to the endpoint device108, a vice-versa. The communication session 202 may include varioustypes of communication media, such as voice, video, messaging, content,and so forth.

According to various implementations, the client device 102 communicatesdata of the communication session 202 in a packetized form to the corenetwork 112. The core network 112 processes the data packets into a formthat can be utilized by the radio network 114, and communicates theprocessed packets to the radio network 114. The radio network 114converts the processed packets into wireless signal which is transmittedfor receipt by the endpoint device 108 as part of the communicationsession 202.

Further to the scenario 200, the communication session 202 is initiallyrouted across the core network 112 utilizing a standard (e.g., default)routing path (“standard path”) 204. The standard path 204, for instance,represents a default path that is utilized for routing general mediaflows across the core network 112. In at least some implementations, thestandard path 204 is utilized for routing media flows according to abest effort CoS.

Further, the communication session 202 is initially transmitted by theradio network 114 to the endpoint device 108 utilizing a default bearer(“default”) channel 206. The default channel 206, for instance,represents a general wireless channel and/or collection of wirelesschannels that is used for wireless data communication.

In response to initiation of the communication session 202, thecommunication service 106 communicates an initiation notification 208 tothe proxy module 122. The communication session 202, for instance, isinitiated and/or managed via the communication service 106, and thus thecommunication service 106 has awareness of various attributes of thecommunication session 202. In at least some implementations, thenotification 208 is generated using the communication API discussedabove. Attributes of the communication API, for instance, are populatedat least in part with values that identify various attributes of thecommunication session, which are then utilized to generate thenotification 208. Example attributes indicated by the notification 208includes identifiers for users and/or devices involved in thecommunication session (e.g., the client device 102 and the endpointdevice 108), media type(s) included, service level (e.g., “prioritized,”“standard,” and so forth), and so on.

The proxy module 122 receives the notification 208 and translates theattributes included in the notification 208 into a protocol utilized bythe core network 112. The proxy module 122 generates a sessionnotification 210, populates the session notification 210 with thetranslated attributes, and communicates the notification 210 to thepolicy module 118. The policy module 118 processes the notification 210to identify the translated attributes of the communication session 202,and utilizes the translated attributes to engage in a configurationevent 212 with the traffic processor 116. Generally, the configurationevent 212 involves propagating at least some of the translatedattributes from the session notification 210 to the traffic processor116, which causes a communication policy 120 a to be generated. Thepolicy module 118, for instance, programs the traffic processor 116 withthe translated attributes to generate the communication policy 120 a.The communication policy 120 a represents an instance of thecommunication policies 120 introduced above. While a singlecommunication policy 120 a is depicted in the scenario 200, it is to beappreciated that the traffic processor 116 may maintain and enforcemultiple different communication policies 120 across multiple differentcommunication sessions.

According to various implementations, the communication policy 120 a isgenerated specifically for the communication session 202 and specifiesactions and/or behaviors to be performed in relation to thecommunication session 202. For instance, the communication policy 120 aincludes identification information that enables the traffic processor116 to differentiate the media flow of the communication session 202from other media flows. Further, the communication policy 120 aspecifies that the media flow (e.g., data packets) of the communicationsession is to be marked with a prioritized QoS marking, such as AssuredForwarding. As further detailed below, the traffic processor 116 appliesthe communication policy 120 a to give priority treatment to thecommunication session 202.

Continuing with the scenario 200, the policy module 118 initiates aconfiguration event 214 with the radio network 114. Generally, theconfiguration event 214 includes identification information thatidentifies the communication session 202 and enables the radio network114 to differentiate a media flow of the communication session 202 fromother media flows. Further, the configuration event 214 instructs theradio network 114 to move the communication session to a prioritizedchannel. As further detailed below, the radio network 114 moves thecommunication session 202 to a prioritized channel in response to theconfiguration event 214.

FIG. 3 illustrates an example implementation scenario 300 forprioritizing a communication session in accordance with one or moreimplementations. The scenario 300, for instance, represents acontinuation of the scenario 200 and includes various entities andcomponents introduced above with reference to the environment 100.

In the scenario 300, the traffic processor 116 applies the communicationpolicy 120 a to the communication session 202. For instance, the trafficprocessor 116 marks data of the communication session 202 with aprioritized QoS marking, such as Assured Forwarding. In at least someimplementations, the communication session 202 is initially marked witha default QoS when it is initiated, such as Best Effort. Accordingly,the traffic processor 116 applies the communication policy 120 a toremark the communication session 202 from a default QoS (e.g., lowerQoS) to a prioritized QoS.

In response to remarking the communication session 202 to theprioritized QoS, the communication session 202 is rerouted from thestandard path 204 to a prioritized routing path (“prioritized path”) 302across the core network 112. Generally, the prioritized path 302represents a secure routing path across the core network 112 thatprovides enhanced service over the standard path 204, such as fastersignal traversal, higher signal quality, and/or greater data securityacross the core network 112.

According to various implementations, the traffic processor 116 enforcesa security policy that indicates that only authenticated trusted mediaflows are permitted to traverse the core network 112 and be passed on tothe radio network 114. Enforcing such a security policy assists inprotecting the core network 112 and the radio network 114 from maliciousactivities, such as malware, Denial-of-Service (DoS) attacks, and soforth, that may be introduced in an untrusted and/or unauthenticatedmedia flow. Accordingly, when the communication session 202 is firstinitiated, the communication session 202 is routed across the standardchannel 204. Generally, the standard channel 204 represents a channelthat is used for temporarily routing unauthenticated media flows acrossthe core network 112. For instance, the standard channel 204 is isolatedfrom primary infrastructure components of the core network 112. Further,media flows across the standard channel 204 may be monitored forattributes and/or behaviors that are indicative of malicious activities.Configuration of the communication policy 120 a, however, indicates thatthe communication session 202 is an authenticated and trusted mediaflow. Thus, the communication session 202 is marked with a prioritizedQoS and is rerouted to the prioritized path 302. The prioritized path302, for instance, is reserved for trusted and/or authenticated mediaflows, and provides such media flows with enhanced service over thestandard path 204.

Continuing with the scenario 300, and in response to the configurationevent 214 discussed above, the radio network 114 moves the communicationevent 202 from the default channel 206 to a dedicated bearer channel(“dedicated channel”) 304. Generally, the dedicated channel 304represents a channel and/or set of channels that are configured toprovide enhanced wireless service as compared to the default channel206. For instance, the dedicated channel 304 provides the communicationsession 202 with a higher airtime prioritization than does the defaultchannel 206. Thus, the scenario 300 illustrates that based oninteraction by the communication service 106 with components of the corenetwork 112 and the radio network 114, the communication session 202 ismoved from a default media path (e.g., the standard path 204 and thedefault channel 206) to a prioritized media path, e.g., the prioritizedpath 302 and the prioritized channel 304.

Accordingly, the scenarios 200, 300 illustrate that techniques fornotification for a prioritized media path for a communication sessiondiscussed herein enable media flows authenticated with the communicationservice 106 to be provided with increased service levels acrossdifferent networks involved in routing the media flows. This not onlyenables increased quality of service for media flows, but protectsnetworks and services from malicious activities that may result fromunauthenticated media flows.

In at least some implementations, when the communication session 202 isterminated, the communication session is moved back to the standard path204 and the default channel 206 during the termination process. Further,the communication policy 120 a may be cancelled (e.g., deleted) suchthat a subsequent unauthenticated media flow cannot attempt to spoof thecommunication session 202 and thus be routed through prioritized pathsand/or channels across the different networks.

According to various implementations, the rerouting described above isimplemented without disconnecting and/or interrupting the communicationsession 202, independent of user input, and/or independent of a userbeing notified. Thus, seamless rerouting can be effected with little orno negative impact on a user experience during a communication session.Further, the scenarios 200, 300 may be performed on a per-session basisto generate communication policies that are specific the discreteinstances of communication sessions.

According to various implementations, the different notifications andevents discussed in the implementation scenarios can be communicatedseparately and independently (“out-of-band”) from a media flow of thecommunication session 202.

The example implementation scenarios presented above are discussed withreference to discrete devices and discrete sets of media paths forpurpose of example only. It is to be appreciated, however, thatembodiments may be employed in a variety of different networks and withmultiple different devices not expressly discussed herein. Further,connection scenarios are often dynamically changing, and thus techniquesdiscussed herein may be applied dynamically to map and remap media pathsto account for changes in connection attributes.

Having discussed some example implementation scenarios, consider now adiscussion of some example procedures in accordance with one or moreembodiments.

Example Procedures

The following discussion describes some example procedures fornotification for a prioritized media path for a communication session inaccordance with one or more embodiments. The example procedures may beemployed in the environment 100 of FIG. 1, the system 600 of FIG. 6,and/or any other suitable environment. In at least some implementations,the steps described for the various procedures can be implementedautomatically and independent of user interaction. The procedures, forinstance, represent example ways of performing various aspects of theimplementation scenarios described above.

FIG. 4 is a flow diagram that describes steps in a method in accordancewith one or more embodiments. The method describes an example procedurefor causing a communication session to be routed to a prioritized mediapath in accordance with one or more embodiments.

Step 400 ascertains one or more attributes of a communication sessionthat is initiated between a client device and an endpoint device. Thesession module 124 of the communication service 106, ascertainsattributes of the communication session 202. Examples of differentsession attributes are discussed above, such as with reference to thecommunication API. In at least some implementations, the one or moreattributes are received by a communication component of thecommunication service 106.

Step 402 determines that the communication session is authenticated witha communication service for a prioritized media path. For instance, thesession module 124 determines that a user that initiates thecommunication session is authenticated with the communication service106. The user, for instance, has a valid user profile with thecommunication service 106 that entitles the user to prioritized service.

Step 404 forms a notification that includes the one or more attributesand an indication that the communication session is authenticated for aprioritized media path. The session module 124, for example, generates anotification that includes attributes of the communication session, andthat indicates that the communication session is permitted to be routedto one or more prioritized media paths. In at least someimplementations, the notification is formed utilizing the communicationAPI detailed above. For instance, the notification is populated withvalues for one or more of the attributes described with reference to thecommunication API. One example of a suitable notification is describedabove with reference to the initiation notification 208.

Step 406 communicates the notification to a network proxy to cause thecommunication session to be marked with a prioritized class of serviceindicator and to be routed to a prioritized media path. The sessionmodule 124, for instance, communicates the notification to the proxymodule 122. The proxy module 122 translates attributes of thenotification into a protocol that is recognized by the core network 112.The proxy module 122 communicates the translated attributes to thepolicy module 118, which interacts with the traffic processor 116utilizing the translated attributes to configure a communication policywhich indicates that the communication session is to be marked with aprioritized QoS indicator. Accordingly, the communication policy isenforced at the traffic processor 116 such that the communicationsession is marked at the core network 112 with a prioritized class ofservice indicator and is routed to a prioritized path across the corenetwork 112. For instance, the communication session 202 is reroutedfrom the standard path 204 to the prioritized path 302.

The policy module 118 further interacts with a radio access network(e.g., the radio network 114) to cause the communication session to berouted at the radio access network from a standard wireless channel to aprioritized wireless channel for receipt by the endpoint device. Theradio access network, for instance, reroutes the communication session202 from the default channel 206 (e.g., a standard bearer channel) tothe prioritized channel 304, e.g., a dedicated bearer channel.

FIG. 5 is a flow diagram that describes steps in a method in accordancewith one or more embodiments. The method describes an example procedurefor causing a communication session to be rerouted in accordance withone or more implementations. The procedure, for instance, represents anextension of the procedure described above. For example, the procedureis applied to reroute a communication session that has been previouslyrouted to a prioritized media path according to the procedure andscenarios described above.

Step 500 receives an indication of a session problem in a communicationsession. The communication service 106, for instance, receives anotification from the client device 102 (e.g., from the communicationclient 110 a) that a problem occurs during the communication session202. For example, the notification indicates one or more of errors thatoccur in communication session data, a decrease in signal quality,problems with user experience during the communication session, and soforth.

Step 502 forms a notification indicating that the communication sessionis to be rerouted. For instance, the session module 124 generates anotification that identifies the session problem(s), and that indicatesthat the communication session is to be rerouted to a different mediapath. In at least some implementations, the notification is generatedusing the communication API detailed above, such as using attributes ofthe described Session Problem Events.

Step 504 communicates the notification to a network proxy to cause thecommunication session to be rerouted to a different media path. Thesession module 124, for instance, communicates the notification to theproxy module 122. The proxy module 122 translates attributes of thenotification into a protocol that is recognized by the core network 112.The proxy module 122 communicates the translated attributes to thepolicy module 118, which interacts with the traffic processor 116utilizing the translated attributes to configure a communication policywhich indicates that the communication session is to be rerouted to adifferent media path. Accordingly, the communication policy is enforcedat the traffic processor 116 such that the communication session isrerouted to a different media path. For instance, the communicationsession 202 is rerouted from the prioritized path 302 to a differentprioritized path across the core network 112.

Alternatively or additionally to rerouting at the core network 112, theproxy module 122 may interact with the radio network 114 to cause thecommunication session to be rerouted to a different bearer channel. Forinstance, the current dedicated bearer channel being used to route thecommunication session may be experiencing signal quality problems, suchas based on signal interference, excessive traffic, and so forth. Thus,the communication session can be rerouted by the radio network 114 to adifferent dedicated channel, such as a channel that is known thatprovide higher signal quality and/or that has less signal traffic.Accordingly, techniques discussed herein can be employed to reroutecommunication sessions to mitigate session problems.

According to various implementations, the various aspects of theimplementations scenarios and procedures described above are performedwithout handling data of a communication session. For instance, thesession module 124 receives attributes of communication sessions andpropagates attributes of the communication sessions without receivingand handling media data of the communication sessions. Further,attributes of a communication sessions are propagated separately (e.g.,out-of-band) from a media flow of the communication session and inreal-time while the communication session is in progress.

Accordingly, techniques described herein enable a media flow of anauthenticated communication session to be routed across a prioritizedmedia path and/or set of prioritized media paths. Thus, session qualityfor the communication session can be increased. Further, networks thatmaintain prioritized media paths can be protected from unauthenticatedmedia flows that may degrade network performance and/or introducemalicious activities into the networks.

Having discussed some example procedures, consider now a discussion ofan example system and device in accordance with one or more embodiments.

Example System and Device

FIG. 6 illustrates an example system generally at 600 that includes anexample computing device 602 that is representative of one or morecomputing systems and/or devices that may implement various techniquesdescribed herein. For example, the client device 102, the endpointdevice 108, and/or the communication service 106 discussed above withreference to FIG. 1 can be embodied as the computing device 602. Thecomputing device 602 may be, for example, a server of a serviceprovider, a device associated with the client (e.g., a client device),an on-chip system, and/or any other suitable computing device orcomputing system.

The example computing device 602 as illustrated includes a processingsystem 604, one or more computer-readable media 606, and one or moreInput/Output (I/O) Interfaces 608 that are communicatively coupled oneto another. Although not shown, the computing device 602 may furtherinclude a system bus or other data and command transfer system thatcouples the various components, one to another. A system bus can includeany one or combination of different bus structures, such as a memory busor memory controller, a peripheral bus, a universal serial bus, and/or aprocessor or local bus that utilizes any of a variety of busarchitectures. A variety of other examples are also contemplated, suchas control and data lines.

The processing system 604 is representative of functionality to performone or more operations using hardware. Accordingly, the processingsystem 604 is illustrated as including hardware element 610 that may beconfigured as processors, functional blocks, and so forth. This mayinclude implementation in hardware as an application specific integratedcircuit or other logic device formed using one or more semiconductors.The hardware elements 610 are not limited by the materials from whichthey are formed or the processing mechanisms employed therein. Forexample, processors may be comprised of semiconductor(s) and/ortransistors (e.g., electronic integrated circuits (ICs)). In such acontext, processor-executable instructions may beelectronically-executable instructions.

The computer-readable media 606 is illustrated as includingmemory/storage 612. The memory/storage 612 represents memory/storagecapacity associated with one or more computer-readable media. Thememory/storage 612 may include volatile media (such as random accessmemory (RAM)) and/or nonvolatile media (such as read only memory (ROM),Flash memory, optical disks, magnetic disks, and so forth). Thememory/storage 612 may include fixed media (e.g., RAM, ROM, a fixed harddrive, and so on) as well as removable media (e.g., Flash memory, aremovable hard drive, an optical disc, and so forth). Thecomputer-readable media 606 may be configured in a variety of other waysas further described below.

Input/output interface(s) 608 are representative of functionality toallow a user to enter commands and information to computing device 602,and also allow information to be presented to the user and/or othercomponents or devices using various input/output devices. Examples ofinput devices include a keyboard, a cursor control device (e.g., amouse), a microphone (e.g., for voice recognition and/or spoken input),a scanner, touch functionality (e.g., capacitive or other sensors thatare configured to detect physical touch), a camera (e.g., which mayemploy visible or non-visible wavelengths such as infrared frequenciesto detect movement that does not involve touch as gestures), and soforth. Examples of output devices include a display device (e.g., amonitor or projector), speakers, a printer, a network card,tactile-response device, and so forth. Thus, the computing device 602may be configured in a variety of ways as further described below tosupport user interaction.

The computing device 602 further includes communication components 614,which are representative of functionality to receive and transmit datafor the computing device 602. For instance, the communication components614 represent components for interfacing and communicating with anetwork, such as via any suitable wired and/or wireless protocol.According to various implementations, the communication components 614receive data transmitted to the computing device 602 and route the datato one or more other components of the computing device 602. Further,the communication components 614 receive data from one or more internalcomponents of the computing device 602, and cause the data to becommunicated to various entities (e.g., devices) remote from thecomputing device 602.

Various techniques may be described herein in the general context ofsoftware, hardware elements, or program modules. Generally, such modulesinclude routines, programs, objects, elements, components, datastructures, and so forth that perform particular tasks or implementparticular abstract data types. The terms “module,” “functionality,” and“component” as used herein generally represent software, firmware,hardware, or a combination thereof. The features of the techniquesdescribed herein are platform-independent, meaning that the techniquesmay be implemented on a variety of commercial computing platforms havinga variety of processors.

An implementation of the described modules and techniques may be storedon or transmitted across some form of computer-readable media. Thecomputer-readable media may include a variety of media that may beaccessed by the computing device 602. By way of example, and notlimitation, computer-readable media may include “computer-readablestorage media” and “computer-readable signal media.”

“Computer-readable storage media” may refer to media and/or devices thatenable persistent storage of information in contrast to mere signaltransmission, carrier waves, or signals per se. Computer-readablestorage media do not include signals per se. The computer-readablestorage media includes hardware such as volatile and non-volatile,removable and non-removable media and/or storage devices implemented ina method or technology suitable for storage of information such ascomputer readable instructions, data structures, program modules, logicelements/circuits, or other data. Examples of computer-readable storagemedia may include, but are not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical storage, hard disks, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or otherstorage device, tangible media, or article of manufacture suitable tostore the desired information and which may be accessed by a computer.

“Computer-readable signal media” may refer to a signal-bearing mediumthat is configured to transmit instructions to the hardware of thecomputing device 602, such as via a network. Signal media typically mayembody computer readable instructions, data structures, program modules,or other data in a modulated data signal, such as carrier waves, datasignals, or other transport mechanism. Signal media also include anyinformation delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media include wired media such as awired network or direct-wired connection, and wireless media such asacoustic, radio frequency (RF), infrared, and other wireless media.

As previously described, hardware elements 610 and computer-readablemedia 606 are representative of instructions, modules, programmabledevice logic and/or fixed device logic implemented in a hardware formthat may be employed in some embodiments to implement at least someaspects of the techniques described herein. Hardware elements mayinclude components of an integrated circuit or on-chip system, anapplication-specific integrated circuit (ASIC), a field-programmablegate array (FPGA), a complex programmable logic device (CPLD), and otherimplementations in silicon or other hardware devices. In this context, ahardware element may operate as a processing device that performsprogram tasks defined by instructions, modules, and/or logic embodied bythe hardware element as well as a hardware device utilized to storeinstructions for execution, e.g., the computer-readable storage mediadescribed previously.

Combinations of the foregoing may also be employed to implement varioustechniques and modules described herein. Accordingly, software,hardware, or program modules and other program modules may beimplemented as one or more instructions and/or logic embodied on someform of computer-readable storage media and/or by one or more hardwareelements 610. The computing device 602 may be configured to implementparticular instructions and/or functions corresponding to the softwareand/or hardware modules. Accordingly, implementation of modules that areexecutable by the computing device 602 as software may be achieved atleast partially in hardware, e.g., through use of computer-readablestorage media and/or hardware elements 610 of the processing system. Theinstructions and/or functions may be executable/operable by one or morearticles of manufacture (for example, one or more computing devices 602and/or processing systems 604) to implement techniques, modules, andexamples described herein.

As further illustrated in FIG. 6, the example system 600 enablesubiquitous environments for a seamless user experience when runningapplications on a personal computer (PC), a television device, and/or amobile device. Services and applications run substantially similar inall three environments for a common user experience when transitioningfrom one device to the next while utilizing an application, playing avideo game, watching a video, and so on.

In the example system 600, multiple devices are interconnected through acentral computing device. The central computing device may be local tothe multiple devices or may be located remotely from the multipledevices. In one embodiment, the central computing device may be a cloudof one or more server computers that are connected to the multipledevices through a network, the Internet, or other data communicationlink.

In one embodiment, this interconnection architecture enablesfunctionality to be delivered across multiple devices to provide acommon and seamless experience to a user of the multiple devices. Eachof the multiple devices may have different physical requirements andcapabilities, and the central computing device uses a platform to enablethe delivery of an experience to the device that is both tailored to thedevice and yet common to all devices. In one embodiment, a class oftarget devices is created and experiences are tailored to the genericclass of devices. A class of devices may be defined by physicalfeatures, types of usage, or other common characteristics of thedevices.

In various implementations, the computing device 602 may assume avariety of different configurations, such as for computer 616, mobile618, and television 620 uses. Each of these configurations includesdevices that may have generally different constructs and capabilities,and thus the computing device 602 may be configured according to one ormore of the different device classes. For instance, the computing device602 may be implemented as the computer 616 class of a device thatincludes a personal computer, desktop computer, a multi-screen computer,laptop computer, netbook, and so on.

The computing device 602 may also be implemented as the mobile 618 classof device that includes mobile devices, such as a mobile phone, portablemusic player, portable gaming device, a tablet computer, a wearabledevice, a multi-screen computer, and so on. The computing device 602 mayalso be implemented as the television 620 class of device that includesdevices having or connected to generally larger screens in casualviewing environments. These devices include televisions, set-top boxes,gaming consoles, and so on.

The techniques described herein may be supported by these variousconfigurations of the computing device 602 and are not limited to thespecific examples of the techniques described herein. For example,functionalities discussed with reference to the communication service106 may be implemented all or in part through use of a distributedsystem, such as over a “cloud” 622 via a platform 624 as describedbelow.

The cloud 622 includes and/or is representative of a platform 624 forresources 626. The platform 624 abstracts underlying functionality ofhardware (e.g., servers) and software resources of the cloud 622. Theresources 626 may include applications and/or data that can be utilizedwhile computer processing is executed on servers that are remote fromthe computing device 602. Resources 626 can also include servicesprovided over the Internet and/or through a subscriber network, such asa cellular or Wi-Fi network.

The platform 624 may abstract resources and functions to connect thecomputing device 602 with other computing devices. The platform 624 mayalso serve to abstract scaling of resources to provide a correspondinglevel of scale to encountered demand for the resources 626 that areimplemented via the platform 624. Accordingly, in an interconnecteddevice embodiment, implementation of functionality described herein maybe distributed throughout the system 600. For example, the functionalitymay be implemented in part on the computing device 602 as well as viathe platform 624 that abstracts the functionality of the cloud 622.

Discussed herein are a number of methods that may be implemented toperform techniques discussed herein. Aspects of the methods may beimplemented in hardware, firmware, or software, or a combinationthereof. The methods are shown as a set of steps that specify operationsperformed by one or more devices and are not necessarily limited to theorders shown for performing the operations by the respective blocks.Further, an operation shown with respect to a particular method may becombined and/or interchanged with an operation of a different method inaccordance with one or more implementations. Aspects of the methods canbe implemented via interaction between various entities discussed abovewith reference to the environment 100.

Implementations discussed herein include:

Example 1

A system for prioritizing a communication session, the system including:at least one processor; and one or more computer-readable storage mediaincluding instructions stored thereon that, responsive to execution bythe at least one processor, cause the system perform operationsincluding: ascertaining one or more attributes of a communicationsession that is initiated between a client device and an endpointdevice; determining that the communication session is authenticated fora prioritized media path; forming a notification that includes the oneor more attributes and an indication that the communication session isauthenticated for a prioritized media path; and communicating thenotification to a network proxy to cause the communication session to bemarked with a prioritized class of service indicator and to be routedfrom a standard wireless channel to a prioritized wireless channel forreceipt by the endpoint device.

Example 2

A system as described in example 1, wherein said determining includesdetermining that a user of the client device is authenticated for theprioritized media path.

Example 3

A system as described in one or more of examples 1 or 2, wherein thesystem is configured to perform the operations in real-time while thecommunication session is in progress.

Example 4

A system as described in one or more of examples 1-3, wherein the systemis configured to perform the operations without handling data of thecommunication session.

Example 5

A system as described in one or more of examples 1-4, wherein saidforming includes populating an application programming interface (API)with the one or more attributes, and wherein the notification isformatted at least in part with the API.

Example 6

A system as described in one or more of examples 1-5, wherein saidcommunicating further causes the communication session to be routed froma standard routing path across an Internet Protocol (IP) network to aprioritized routing path across the IP network.

Example 7

A system as described in one or more of examples 1-6, wherein theoperations further include: receiving an indication of a session problemin the communication session; and communicating a notification to causethe communication session to be rerouted from the prioritized wirelesschannel to a different wireless channel.

Example 8

A system as described in one or more of examples 1-7, wherein theoperations further include: receiving an indication of a session problemin the communication session; forming a notification indicating that thecommunication session is to be rerouted; and communicating thenotification to the network proxy to cause the communication session tobe rerouted from the prioritized wireless channel to a differentwireless channel.

Example 9

A computer-implemented method for prioritizing a communication session,the method including: ascertaining one or more attributes of acommunication session that is initiated between a client device and anendpoint device; determining that the communication session isauthenticated with a communication service for a prioritized media path;forming a notification that includes the one or more attributes and anindication that the communication session is authenticated for aprioritized media path; and communicating the notification to a networkproxy to cause the communication session to be marked at an InternetProtocol (IP) network with a prioritized class of service indicator andto be routed at a radio access network from a standard wireless channelto a prioritized wireless channel for receipt by the endpoint device.

Example 10

A method as described in example 9, wherein said forming includes:populating an application programming interface (API) with the one ormore attributes; and generating the notification using the populatedAPI.

Example 11

A method as described in one or more of examples 9 or 10, wherein saidcommunicating includes communicating the notification while thecommunication session is in progress.

Example 12

A method as described in one or more of examples 9-11, wherein saidcommunicating includes communicating the notification separately from amedia flow of the communication session.

Example 13

A method as described in one or more of examples 9-12, wherein saidcommunicating further causes the communication session to be routed froma standard routing path across the IP network to a prioritized routingpath across the IP network.

Example 14

A method as described in one or more of examples 9-13, furtherincluding: receiving an indication of a session problem in thecommunication session; and communicating a notification to the networkproxy to cause the communication session to be rerouted from theprioritized wireless channel to a different wireless channel.

Example 15

A method as described in one or more of examples 9-14, furtherincluding: receiving an indication of a session problem in thecommunication session; and communicating the notification to cause thecommunication session to be rerouted from a current routing path acrossthe IP network to a different routing path across the IP network.

Example 16

A system for prioritizing a communication session, the system including:one or more processors; a communication component configured to receiveone or more attributes of a communication session that is initiatedbetween a client device and an endpoint device; and at least one modulethat is executable by the one or more processors to: determine based onthe one or more attributes that the communication session isauthenticated with a communication service for a prioritized media path;form a notification that includes the one or more attributes and anindication that the communication session is authenticated for aprioritized media path; and communicate the notification to a networkproxy to cause the communication session to be marked at an InternetProtocol (IP) network with a prioritized class of service indicator andto be routed at a radio access network from a standard wireless channelto a prioritized wireless channel for receipt by the endpoint device.

Example 17

A system as described in example 16, wherein the at least one module isconfigured to communicate the notification separately from a media flowof the communication session.

Example 18

A system as described in one or more of examples 16 or 17, wherein theat least one module is configured to communicate the notification inreal-time while the communication session is in progress.

Example 19

A system as described in one or more of examples 16-18, wherein the atleast one module is configured to communicate the notification to causethe communication session to be remarked from a current class of serviceindicator to the prioritized class of service indicator.

Example 20

A system as described in one or more of examples 16-19, wherein the atleast one module is configured to communicate the notification to causethe communication session to be routed from a standard routing pathacross the IP network to a prioritized routing path across the IPnetwork.

CONCLUSION

Techniques for notification for a prioritized media path for acommunication session are described. Although embodiments are describedin language specific to structural features and/or methodological acts,it is to be understood that the embodiments defined in the appendedclaims are not necessarily limited to the specific features or actsdescribed. Rather, the specific features and acts are disclosed asexample forms of implementing the claimed embodiments.

What is claimed is:
 1. A system comprising: at least one processor; andone or more computer-readable storage media including instructionsstored thereon that, responsive to execution by the at least oneprocessor, cause the system to perform operations including:ascertaining, by a service implemented on an Internet Protocol (IP)network, one or more attributes of a communication session that isinitiated via the IP network between a client device and an endpointdevice, the communication session routed from the IP network to awireless network and initially routed at the wireless network over adefault wireless channel of the wireless network to the endpoint device;determining that the communication session is authenticated for aprioritized media path; forming a notification that includes the one ormore attributes and an indication that the communication session isauthenticated for a prioritized media path; and communicating thenotification to a network proxy to cause the communication session to bemarked at the IP network with a prioritized class of service indicatorand to be rerouted, while the communication session is in progress, fromthe default wireless channel to a prioritized wireless channel on thewireless network and for receipt by the endpoint device.
 2. A system asrecited in claim 1, wherein said determining comprises determining thata user of the client device is authenticated for the prioritized mediapath.
 3. A system as recited in claim 1, wherein the system isconfigured to perform the operations in real-time while thecommunication session is in progress.
 4. A system as recited in claim 1,wherein the system is configured to perform the operations withouthandling data of the communication session.
 5. A system as recited inclaim 1, wherein said forming comprises populating an applicationprogramming interface (API) with the one or more attributes, and whereinthe notification is formatted at least in part with the API.
 6. A systemas recited in claim 1, wherein said communicating further causes thecommunication session to be routed from a standard routing path acrossthe IP network to a prioritized routing path across the IP network.
 7. Asystem as recited in claim 1, wherein the operations further include:receiving an indication of a session problem in the communicationsession; and communicating a notification to cause the communicationsession to be rerouted from the prioritized wireless channel to adifferent wireless channel.
 8. A system as recited in claim 1, whereinthe operations further include: receiving an indication of a sessionproblem in the communication session; forming a notification indicatingthat the communication session is to be rerouted; and communicating thenotification to the network proxy to cause the communication session tobe rerouted from the prioritized wireless channel to a differentwireless channel.
 9. A computer-implemented method, comprising:ascertaining one or more attributes of a communication session initiatedvia an Internet Protocol (IP) network and initially routed between aclient device and an endpoint device over a default wireless channel ona radio access network; determining, while the communication session isin progress over the default wireless channel on the radio accessnetwork, that the communication session is authenticated with acommunication service for a prioritized media path; forming anotification that includes the one or more attributes and an indicationthat the communication session is authenticated for a prioritized mediapath; and communication the notification to a network proxy to cause thecommunication session to be marked at the IP network with a prioritizedclass of service indicator and to be rerouted, while the communicationsession is in progress, at the radio access network from the defaultwireless channel to a prioritized wireless channel for receipt by theendpoint device.
 10. A method as described in claim 9, wherein saidforming comprises: wherein said forming comprises populating anapplication programming interface (API) with the one or more attributes;and generating the notification using the populated API.
 11. A method asdescribed in claim 9, wherein said communicating comprises communicatingthe notification while the communication session is in progress.
 12. Amethod as described in claim 9, wherein said communicating comprisescommunicating the notification separately from a media flow of thecommunication session.
 13. A method as described in claim 9, whereinsaid communicating further causes the communication session to be routedfrom a standard routing path across the IP network to a prioritized pathacross the IP network.
 14. A method as described in claim 9, furthercomprising: receiving an indication of a session problem in thecommunication session; and communicating a notification to the networkproxy to cause the communication session to be rerouted from theprioritized wireless channel to a different wireless channel.
 15. Amethod as described in claim 9, further comprising: receiving anindication of a session problem in the communication session; andcommunicating the notification to cause the communication session to bererouted from a current routing path across the IP network to adifferent routing path across the IP network.
 16. A system comprising:one or more processors; and at least one module that is executable bythe one or more processors to: determine based on one or more attributesof a communication session initiated via an Internet Protocol (IP)network and initially routed at a radio access network over a defaultwireless channel that the communication session is authenticated with acommunication service for a prioritized media path; form a notificationthat includes the one or more attributes and an indication that thecommunication session is authenticated for a prioritized media path;communicate the notification to a network proxy to cause a communicationpolicy to be generated that indicates that the communication session isauthenticated for a prioritized media path, and to cause thecommunication session to be marked at the IP network with a prioritizedclass of service indicator and to be rerouted at the radio accessnetwork, while the communication session is in progress, from thedefault wireless channel to a prioritized wireless channel for receiptby the endpoint device; determine that the communication session isterminated; and communicate a further notification to the network proxyindicating that the communication session is terminated to cause thecommunication policy to be cancelled.
 17. A system as described in claim16, wherein the at least one module is configured to communicate thenotification separately from a media flow of the communication session.18. A system as described in claim 16, wherein the at least one moduleis configured to communicate the notification in real-time while thecommunication session is in progress.
 19. A system as described in claim16, wherein the at least one module is configured to communicate thenotification to cause the communication session to be remarked from acurrent class of service indicator to the prioritized class of serviceindicator.
 20. A system as described in claim 16, wherein the at leastone module is configured to communicate the notification to cause thecommunication session to be routed from a standard routing path acrossthe IP network to a prioritized routing path across the IP network.